Don't use VPIO forcelist by default #244
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes it so clients have to opt into the VPIO forcelist. It is currently mainly needed by gecko, since sites may create multiple streams to a builtin device with different prefs and processing params, and HAL audio units to builtin device are not working properly when there is a VPIO audio unit to the same builtin device on (anywhere) on the system.
With the cfg flag vpio-forcelist a client can avoid VPIO altogether, by not compiling with the flag, and by never creating input streams with the VOICE pref.
Should a client need to mix VOICE and non-VOICE input streams to a single device, it should enable vpio-forcelist.
Fixes #242.